-
-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Unable to view details of product after scanning #1726
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1726 +/- ##
==========================================
- Coverage 8.86% 8.27% -0.60%
==========================================
Files 161 165 +4
Lines 6623 7145 +522
==========================================
+ Hits 587 591 +4
- Misses 6036 6554 +518
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no time to double-check now, and I'll have no time tomorrow (Sunday May 1st).
OK it looks fair to add ContinuousScanModel in main.dart, but I would be VERY surprised if you don't impact ALL the other places in the code that called/created an instance of ContinuousScanModel
. It's like a singleton. But if it's also created somewhere else, that's a call for confusion and bugs.
Hi @monsieurtanuki, SummaryCard in full screen(cross not required) SummaryCard not in full screen(cross required to remove from carousel) I also checked the impact at onboarding which caused #1720 and everything works fine there. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @bhattabhi013!
I have no strong opinion about when to put the cross, except that we should check first if the product is in the scan carousel if the idea is to put a button to remove the product from the carousel.
But, my main concern is that we should call only once in the whole app await ContinuousScanModel().load(localDatabase)
. Please fix that first.
Hi @monsieurtanuki, |
I think what he means it that we now have two Providers of type ContinuousScanModel but only one should be in the whole widget tree |
@bhattabhi013 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @bhattabhi013, it looks more like that indeed!
Still, I think we could load
the model at init time too, right?
Please have a look at my comments and suggestions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @bhattabhi013!
I just have minor suggestions; feel free to ignore them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bhattabhi013 Let's try it that way!
Possibly, your changes may have a bad impact on the screenshot generation, but that's another story!
Thanks, @monsieurtanuki, |
I don't think it's appropriate to use logic regarding screenshot generation. Just painful experiments do the trick. Believe me! |
What
Fixes Unable to view details of the product after scanning.
Screenshot
Fixes bug(s)
Part of
(please be as granular as possible)